Universal visitor identification system

ABSTRACT

A tag management system can include features to assist in developing a cross-vendor profile for individual visitors to content pages of a content site. The visitors to the content site can obtain universal identifiers usable by the content site to identify the visitors. The universal identifiers can be included in the content pages by the visitor end user systems so that browser tags that may not have native access to the universal identifier can access the universal identifiers. The universal identifiers may then be provided to tag vendor systems with associated visitor data, thereby enabling the tag vendor systems to provide processed or raw data that can be compared by individual universal identifiers. Using this processed data, the content site can prepare the cross-vendor profile of individual visitors and realize insights that may be unavailable using conventional systems and methods.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/091,447, filed Nov. 6, 2020, entitled “UNIVERSAL VISITORIDENTIFICATION SYSTEM,” which is a continuation of U.S. patentapplication Ser. No. 16/403,272, filed May 3, 2019, entitled “UNIVERSALVISITOR IDENTIFICATION SYSTEM,” which is a continuation of U.S. patentapplication Ser. No. 15/622,468, filed Jun. 14, 2017, entitled“UNIVERSAL VISITOR IDENTIFICATION SYSTEM,” which is a continuation ofU.S. patent application Ser. No. 14/629,989, filed Feb. 24, 2015,entitled “UNIVERSAL VISITOR IDENTIFICATION SYSTEM,” which is adivisional of U.S. patent application Ser. No. 14/532,771, filed Nov. 4,2014, entitled “UNIVERSAL VISITOR IDENTIFICATION SYSTEM,” which claimspriority under 35 U.S.C. § 119(e) as a nonprovisional application of thefollowing U.S. Provisional Application:

App. No. Filing Date Title Attorney Docket 61/900,274 Nov. 5, 2013UNIVERSAL VISITOR TEALM.003PR IDENTIFICATION SYSTEM

In addition, this application is related to U.S. application Ser. No.14/149,717, filed Jan. 7, 2014, titled “Content Site Visitor ProcessingSystem” U.S. application Ser. No. 14/151,700, filed Jan. 9, 2014, titled“Combined Synchronous and Asynchronous Tag Deployment,” and U.S.application Ser. No. 14/525,031, filed Oct. 27, 2014, titled “System forPrefetching Digital Tags.” The disclosures of each of the foregoingapplications are hereby incorporated by reference in their entirety.Further, any subset of the embodiments described herein can beimplemented in combination with any subset of the embodiments describedin the foregoing applications.

BACKGROUND

Some operators of content sites, such as websites, regularly obtain theresults of analytics performed with regard to user interactions on theircontent sites. User analytics can include any type of data regardinginteractions of end users with content sites, among other types of data.There are different approaches to gathering analytics data, one of whichincludes employing the use of tags.

Tags can include small pieces of website code that allow a websiteoperator to measure traffic and visitor behavior, understand the impactof online advertising and social channels, use remarketing and audiencetargeting, or test and improve a content site, among optionally otherfunctions. Adding tags to a content site has typically requiredinvolving a developer to manually insert tag code into one or more pagesof a website.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers are re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate embodiments of the features described herein and not to limitthe scope thereof.

FIG. 1 depicts an embodiment of a computing environment that providesaccess to an analytics system, a visitor intelligence system, and tagvendor systems.

FIG. 2 depicts an embodiment of a universal identifier end user systemprocess.

FIG. 3 depicts an embodiment of a universal identifier contentmanagement system process.

FIG. 4 depicts an embodiment of a universal identifier generationprocess.

FIG. 5 depicts an embodiment of a computing environment for identifyingvisitors to a content site using the computing environment of FIG. 1 .

FIG. 6 depicts an embodiment of a computing environment for identifyingvisitors across different content sites using the computing environmentof FIG. 1 .

FIG. 7 depicts an embodiment of a reporting user interface.

FIG. 8 depicts another embodiment of a computing environment, whichprovides distributed cloud-based access.

DETAILED DESCRIPTION I. Tag Management Overview

Adding tags to web pages without efficient management can createsignificant problems and inconveniences. For instance, code associatedwith multiple tags can bog down a content site and can be a majorperformance drain. Redundant or incorrectly applied tags can alsodistort measurements and result in duplicate costs or missing data. Poortag management can also be time consuming for the information technology(IT) department or webmaster team to add new tags, which may mean thatimportant measurement and marketing programs might be significantlydelayed.

Tag management systems have recently been introduced to improve themanagement of tags. In one embodiment, a tag management system candeploy a single tag or a tag container to a content site. Each page orany subset of pages in the content site can incorporate the tagcontainer as a universal tag that can be used to gather any type ofvisitor data of a visitor to a content site. This tag container can beused to interface with any number of third party vendor tags withoutrequiring, in certain embodiments, such tags to be coded expressly inthe code of the content pages (such as web pages) of the content site.Thus, changes to the tagging of a content site may be made through auser interface provided by the tag management system without having touse a developer to add the tags to the content pages manually. As aresult, the tag management system can be more accessible to peoplewithout IT or programming knowledge.

This tag container approach to tag management can promote highscalability and provide marketing agility, enabling marketers and othertag management users to rapidly change data collected or analyzed by thetag management system. Further, since one tag container is embeddedwithin the content pages in certain embodiments, the content pages mayload faster and, therefore, include many performance improvements.Moreover, there may be reduction of IT costs provided by using thedisclosed tag management system because IT personnel can shift away fromperforming tag management work to focusing on IT work.

II. End User Identification Via Tag Management

Tags can provide data about content site visitors to a variety ofanalysis systems hosted by third-party tag vendors. These analysissystems may include, for example, data management platforms (DMP) or webanalytics systems that perform vendor-specific processing on the data toobtain insights about visitors to a content site. These analysis systemsoften operate independently of one another from vendor to vendor andspecialize in providing different insights from the collected data.After the analysis systems complete their processing, a provider of thecontent site can access reports on the processed data from the analysissystems and evaluate the reports to assist with making businessdecisions, such as how to manage the content site or advertise to itsvisitors. Increasingly, content site providers are also requesting theraw data from third-party tag vendors so that the providers can performtheir own processing to obtain further insights about visitors to theircontent sites.

In currently-available systems, the processed data is often given to thecontent site provider in an aggregated form. The processed data may beorganized according to individual tag vendor approaches, making itdifficult if not impossible to determine which portions of the processeddata relate to any particular visitor. It can thus also be exceedinglychallenging to determine what portions of the processed data fromdifferent tag vendors relate to the same visitor. Moreover, even if tagvendors provide the raw collected visitor data to content siteproviders, different tag vendors tend to use different identificationschemes to identify the site visitors. It is therefore often impossibleor highly difficult to correlate this siloed data on each visitor acrosstag vendors. Consequently, neither the processed data nor the raw datafrom different tag vendor systems can be easily evaluated or compared onan individual visitor basis, and thus important insights about visitorsto content sites may be lost.

This disclosure describes embodiments of a tag management system thatcan include features that facilitate developing a cross-vendor profilefor individual visitors of a content site. For instance, the tagmanagement system may enable tag management users to deploy anidentifier tag accessible from content pages of a content site that canfacilitate creation of a universal identifier for visitors of thecontent site or even across content sites. Thus, each visitor system tothe content page may have a unique universal identifier. One or moreother third party tags associated with the tag container can pass thisuniversal identifier to multiple tag vendor systems along with visitordata. The tag vendor systems may use the universal identifier providedwith the visitor data to separately track visitor data related toindividual visitors. As a result, the tag vendor systems can associateprocessed data that may be based in part on particular visitor data withcorresponding individual universal identifiers and visitors. In turn,when the processed or raw visitor data is gathered by a provider of thecontent site from the tag vendor systems, the provider of the contentsite can evaluate the gathered data using the universal identifiers. Thecontent site can thereby develop a cross-vendor profile for individualvisitors and extract significant insights that may otherwise be missedusing conventional systems. In certain embodiments, such a cross-vendorprofile additionally can desirably be developed without relying on avisitor to log in or provide personally identifiable information (suchas an email address, member number, or the like). As used herein, theterm “universal identifier,” in addition to having its ordinary meaning,can signify the capability to use an identifier with every content sitethroughout an entire domain or across multiple domains, such as over anentire network (e.g., the Internet) or optionally some subset thereof,such that the identifier is usable to uniquely identify an end userdevice or an end user.

In an embodiment, a method of identifying user data associated with auser of a content page can be performed under control of a physicalcomputing device including digital logic circuitry. The method caninclude: receiving a content page from a content site, the content pageincluding a data collection tag container that references a plurality oftags stored on a tag server, the plurality of tags comprising a firsttag including first instructions and a second tag including secondinstructions; requesting, from the tag server, the plurality of tagsreferenced by the data collection tag container; programmaticallyexecuting the first instructions of the first tag and the secondinstructions of the second tag; according to the first instructions,obtaining an identifier usable by the content site to identify thephysical computing device, and modifying a portion the content page toinclude the identifier to enable the second tag that does not havenative access to the identifier to access the identifier by reading themodified portion of the content page; and according to the secondinstructions, obtaining the identifier from the modified portion of thecontent page and user data indicative of interactions with the contentsite, and transmitting the identifier and the user data to a pluralityof processing systems, thereby enabling the plurality of processingsystems to associate the user data with the identifier.

The method of the preceding paragraph can include one or more of thefollowing features: The modifying can include adding the identifier to adata layer or a data object associated with a document object model(DOM) of the content page. The obtaining the identifier usable by thecontent site to identify the physical computing device can includegenerating the identifier using an algorithm. The obtaining theidentifier usable by the content site to identify the physical computingdevice can include: transmitting a first cookie associated with thecontent site and a second cookie associated with an identificationsystem to the identification system, the first cookie corresponding to adomain of the content site and a second cookie corresponding to a domainof the identification system; and in response to said transmitting thefirst and second cookies, receiving the identifier from theidentification system. The first cookie can include a first-partycookie, and the second cookie can include a third-party cookie includingthe identifier.

In another embodiment, a method of identifying user data associated witha user of a content page can be performed under control of a user systemcomprising a physical computing device including digital logiccircuitry. The method can include: receiving a first identifier tag anda plurality of first digital tags, the first identifier tag and theplurality of first digital tags associated with a first content pagereceived from a first content site; programmatically executing the firstidentifier tag to obtain an identifier for the user system and to modifythe first content page to include the identifier; programmaticallyexecuting the plurality of first digital tags to obtain the identifierfrom the modified first content page and first additional analytics dataassociated with the first content page and to transmit the identifierand the first additional analytics data to remote computing systems.

The method of the preceding paragraph can include one or more of thefollowing features: The transmission of the identifier to the remotecomputing systems can enable a provider of the first content site toaggregate by the identifier data determined by the remote computingsystems based on the first additional analytics data. The executing thefirst identifier tag can include executing the first identifier tag tomodify the first content page to add the identifier to a data object ora data layer of the first content page. The obtaining the identifier forthe user system can include determining the identifier using anidentifier generation algorithm. The obtaining the identifier for theuser system can include determining the identifier by looking up theidentifier in a data file stored on the user system and associated withthe first content site. The data file can include a cookie. The methodcan further include: receiving a second identifier tag and a pluralityof second digital tags, the second identifier tag and the plurality ofsecond digital tags associated with a second content page received froma second content site; programmatically executing the second identifiertag to obtain the identifier from an identification system separate fromthe user system and to modify the second content page to include theidentifier; and programmatically executing the plurality of seconddigital tags to obtain the identifier from the modified second contentpage and second additional analytics data associated with the secondcontent page and to transmit the identifier and the second additionalanalytics data to the remote computing systems. The first content sitecan correspond to a first domain different from a second domain to whichthe second content site corresponds. The obtaining the identifier fromthe identification system can include: transmitting, to theidentification system, a first data file associated with the secondcontent site and a second data file including the identifier andassociated with the identification system; and in response to saidtransmitting the first and second data files, receiving the identifierfrom the identification system.

In yet another embodiment, a system for identifying user data associatedwith a user of a content page is disclosed. The system can include oneor more memory devices and one or more hardware processors incommunication with the one or more memory devices. The one or morememory devices can be configured to store: a first identifier tag and aplurality of first digital tags, the first identifier tag and theplurality of first digital tags associated with a first content pagereceived from a first content site, and an identifier for the usersystem and the first content site. The one or more hardware processorscan include digital logic circuitry configured to: programmaticallyexecute the first identifier tag to modify the first content page toinclude the identifier, and programmatically execute the plurality offirst digital tags to obtain the identifier from the modified firstcontent page and first additional analytics data associated with thefirst content page and to transmit the identifier and the firstadditional analytics data to remote computing systems.

The system of the preceding paragraph can include one or more of thefollowing features: The digital logic circuitry can be configured toprogrammatically execute the first identifier tag to modify the firstcontent page to add the identifier to a data object or a data layer ofthe first content page. The digital logic circuitry can be configured toobtain the identifier for the user system by determining the identifierusing an identifier generation algorithm. The digital logic circuitrycan be configured to obtain the identifier for the user system bylooking up the identifier in a data file stored on the user system andassociated with the first content site. The data file can include acookie. The one or more memory devices can be further configured to:store a second identifier tag and a plurality of second digital tags,the second identifier tag and the plurality of second digital tagsassociated with a second content page received from a second contentsite; and the digital logic circuitry can be further configured to:programmatically execute the second identifier tag to obtain theidentifier from an identification system separate from the user systemand to modify the second content page to include the identifier, andprogrammatically execute the plurality of second digital tags to obtainthe identifier from the modified second content page and secondadditional analytics data associated with the second content page and totransmit the identifier and the second additional analytics data to theremote computing systems. The first content site can correspond to afirst domain different from a second domain to which the second contentsite corresponds. The digital logic circuitry can be configured toobtain the identifier from the identification system by: transmitting,to the identification system, a first data file associated with thesecond content site and a second data file including the identifier andassociated with the identification system; and in response to saidtransmitting the first and second data files, receiving the identifierfrom the identification system.

For purposes of summarizing the disclosure, certain aspects, advantagesand novel features of several embodiments are described herein. It is tobe understood that not necessarily all such advantages can be achievedin accordance with any particular embodiment of the embodimentsdisclosed herein. Thus, the embodiments disclosed herein can be embodiedor carried out in a manner that achieves or optimizes one advantage orgroup of advantages as taught herein without necessarily achieving otheradvantages as may be taught or suggested herein.

III. Example Visitor Processing Systems and Methods

Turning to FIG. 1 , an embodiment of a computing environment 100 isshown for implementing various tag features, including some or all ofthe identification and tag management features described above. In thecomputing environment 100, one or more end user systems 102 communicateover a network 108 with a content site 110. The end user systems 102 caninclude any form of computing device and may be desktops, laptops,smartphones, tablets, or the like. A browser 103 or other applicationsoftware installed in the end user systems 102 accesses one or morecontent pages 112 of the content site 110. The content pages 112 may beweb pages or other documents or files that may be accessed remotely andprovided to the end user systems 102. Accordingly, the content pages 112may be web pages, documents (e.g., .pdf documents), videos, images,text, combinations of the same, or the like. The content site 110 may bea website, a web server, an application server, a database server,combinations of the same, or the like. Further, the network 108 caninclude a local area network (LAN), a wide area network (WAN), a companyintranet, the public Internet, combinations of the same, or the like.

As shown, one or more content pages 112 of the content site 110 caninclude a tag container 114. The tag container 114 can be an example ofthe tag container described above and can be a universal tag that isinstalled or incorporated in one or more content pages 112 in place of,or instead of, incorporating numerous tags in each page. The tagcontainer 114 can communicate with one or more data collection tags 116,118 (sometimes referred to as digital marketing tags or simply digitaltags) implemented on one or more tag servers 120. Both the content site110 and the tag servers 120 can be implemented in computer hardwareand/or software. The tags 116, 118 can include third-party tags 116provided by tag vendors that are different entities than an operator of,or provider of, the tag container 114. In addition, the tags 116, 118can include a visitor tag or tags 118 that can be provided by the sameprovider as the provider of the tag container 114 (or a differentprovider in some embodiments). Upon execution in the browser 103, thetags 116, 118 can supply visitor identification or other data to avisitor processing system 140, a tag management system 150, or tagvendor systems 170 (optionally through the tag servers 120). In someembodiments, the tag container 114 can be considered a tag, even if thetag container 114 merely calls other tags for execution. Also, the tagcontainer 114 can collect data in addition to calling other tags in someembodiments.

An analytics system 130 is shown in communication with the tag servers120. The analytics system 130 can be implemented in computer hardwareand/or software. For instance, the analytics system 130 may beimplemented in physical and/or virtual servers, which may begeographically dispersed or co-located. In the depicted embodiment, theanalytics system 130 includes the visitor processing system 140 and thetag management system 150, as well as a visitor profile data repository160. The tag management system 150 also includes an identificationsubsystem 152. The visitor processing and tag management systems 140,150 are shown separately for illustrative purposes, although theirfunctionality may be implemented by a single system. The analyticssystem 130 can also be implemented without the tag management system150, and thus, the functionality of the visitor processing system 140can be implemented independent of any tag management or identificationfunctionality. Further, the analytics system 130 can be implementedwithout the visitor processing system 140, and thus, the functionalityof the tag management system 150 can be implemented independent of anyvisitor processing functionality.

In certain embodiments, the visitor processing system 140 can enable tagmanagement users to configure the types of data tracked for differentvisitors of the content site 110, as well as analyze and report on thisvisitor data. For instance, in one embodiment, the visitor processingsystem 140 can provide one or more user interfaces that enablecustomization of collecting information about visitors to the contentsite 110. This information can be obtained initially by the visitortag(s) 118, which may be provided through the tag container 114 to theend user systems 102 for execution in the browser 103. Upon execution inthe browser 103, the visitor tag(s) 118 can supply visitor data to thevisitor processing system 140 (optionally through the tag servers 120).Such visitor data can be stored in visitor profiles in the visitorprofile data repository 160, which may include physical computerstorage. Tag management users can subsequently query the visitorprofiles to obtain reports or other information about visitors to thecontent site 110.

The tag management system 150 can be used to manage the tags 116provided by third-party vendors. For instance, the tag management system150 can provide functionality for tag management users to select whichthird-party vendor tags 116 to associate with the tag container 114 fora variety of vendor-specific processing purposes. These purposes caninclude obtaining analytics for data analysis or business intelligence,tracking affiliate activity with respect to the content site 110,obtaining user data for displaying targeted ads, obtaining user data forcustomizing search functionality or email campaigns targeted to the endusers, obtaining user data for personalizing content of the contentpages 112, obtaining user data for integration with social networkingfunctionality, obtaining user data for big data analysis, combinationsof the same, or the like. Tags for any of these vendor-specificprocessing purposes, among others, can be considered digital tags. Datacollected by the tags 116 can be provided to tag vendor systems 170,which can perform any of this vendor-specific processing. The data orrelated data may additionally or alternatively be passed to the tagvendor systems 170 through the content site 110, the tag server 120, orthe tag management system 150.

In an embodiment, the tag management system 150 provides functionality(such as one or more user interfaces) for tag management users to mapdata sources in the content pages 112 to data sources gathered by thethird-party vendor tags 116. For instance, if one of the content pages112 includes a shopping cart value named “cart value,” the tagmanagement system can provide a user interface that enables a user totell the tag management system 150 to collect data on the “cart value”and map this data to a “cart_value” variable of one of the tags 116. Inaddition, the tag management system 150 can provide similarfunctionality for identifying which data sources of the content pages112 are to be gathered by the visitor tag 118.

However, in some embodiments, the visitor tag 118 can instead perform agreedy collection of some or all data available in the content page(s)112. Since the visitor tag 118, tag container 114, and visitorprocessing system 140 can be provided by the same entity, the dataobtained by the visitor tag 118 need not be mapped to third-partymappings like the data obtained by the third-party tags 116. Instead,some or all of the data available to the visitor tag 118 can be providedto the visitor processing system 140 for processing. Thus, the visitortag 118 can facilitate vendor-neutral data gathering of some or all ofthe data elements in a content page 112. Since this data may not bemapped to a vendor-specific format in certain embodiments, the data canbe exported to business intelligence systems, such as visitorintelligence system 180, without a need to massage the data from itsmapped form (which can be cumbersome) to its original, raw form.

The browser 103 can execute an identification tag (e.g., the visitor tag118) of the tags 116, 118. The identification tag may include a scriptor the like that causes the browser 103 to obtain a universal identifierand update the content page 112 with the universal identifier. Theuniversal identifier can uniquely identify the end user system 102 tothe content site 110. In some embodiments, upon execution of theuniversal identification tag, the browser 103 can obtain the universalidentifier by generating the universal identifier or retrieve theuniversal identifier from a locally-stored data file. Additionally oralternatively, the browser 103 can obtain the universal identifier bysending visitor identification or other data via the network 108 to anidentification subsystem 152 of the tag management system 150. In turn,the identification subsystem 152 can use the received information toprovide the universal identifier and transmit the universal identifierto the browser 103 via the network 108. Once the universal identifier isobtained, the identification tag can update the code of the content page112 to include the universal identifier. Upon execution of one or moreof the tags 116, 118, the universal identifier updated in the code ofthe content page 112 may then be provided to the visitor processingsystem 140 or the tag vendor systems 170, along with the data about theend user system 102 collected by the tags 116, 118, enabling thecollected data to be identifiable during and after processing by thevisitor processing system 140 or the tag vendor systems 170.

The systems 140, 170 can utilize the universal identifiers provided bythe tags 116, 118 to associate particular raw visitor data and processeddata with individual universal identifiers. The systems 140, 170, forexample, can separately process the collected data associated withindividual universal identifiers. Upon completion of the processing, theprocessed data may be kept separate according to the individualuniversal identifiers. In another example, the systems 140, 170 compileor transform the raw visitor data associated with multiple universalidentifiers and attribute any determined processed data based on the rawdata to each of the multiple individual identifiers.

The systems 140, 170 can provide the processed data to a visitorintelligence system 180, which may be owned, operated, or otherwise usedby an operator of the content site 112 to analyze site visitor behavior.The visitor intelligence system 180 can be implemented in computerhardware and/or software. The visitor intelligence system 180 canreceive the raw data or processed data from the systems 140, 170 andstore and manage the data in a way that facilitates a meaningfulpresentation of information to those interested in the performance ofthe content page 112 of the content site 110. In addition, the visitorintelligence system 180 may organize the presentation of the informationaccording to one or more universal identifiers so that a cross-vendorunderstanding of visitors of the content page 112 may be provided. Incertain embodiments, such an approach advantageously enables the visitorintelligence system 180 to present a more complete picture of individualvisitors and facilitates joining or evaluating disparate processed datasets from the systems 140, 170 using the commonly assigned universalidentifiers. Moreover, this approach can provide flexibility andcustomization options for consumers of the information by enabling theinformation to be viewed according to groups of visitors or according tospecific characteristics of individual visitors. In some embodiments,the visitor intelligence system 180 is part of the visitor processingsystem 140 or the tag management system 150 rather than separate asillustrated in FIG. 1 .

Various tag management user systems 104 can access the tag servers 120,the analytics system 130, or the visitor intelligence system 180 via thenetwork 108. Like the end user systems 102, the tag management usersystems 104 can include a browser 105 or other application software thatcan access network applications over the network 108. The tag managementuser systems 104 can also be any type of computing device including, butnot limited to, a desktop, laptop, tablet, smartphone, or the like. Thetag management user systems 104 can be operated by tag management userssuch as marketing professionals, website operators, business users,operators of the content site 110, or any other individual who uses tagsor data obtained from tags. Tag management users are not the end usersof the content site 110 in certain embodiments. A tag management usermight use a tag management user system 104 to dynamically update thetypes of data tracked or analyzed for different visitors of the contentsite 110. This data can be tracked by the visitor processing system 140via either updating the visitor tag 116 stored on the tag server 120 orby updating processing of data obtained from the visitor tag 116 tobuild updated visitor profiles 160. In addition, tag management userscan access the information stored in the visitor intelligence system 180to obtain a cross-vendor understanding of particular end user systemsfor purposes such as evaluating the effectiveness of various marketingcampaigns, for instance.

Turning to FIG. 2 , an embodiment of a universal identifier end usersystem process 200 is shown. The process 200 illustrates an example modeof operation of the computing environment 100 of FIG. 1 and may beimplemented by the various components shown in the computing environment100 of FIG. 1 . For convenience, the process 200 is described in thecontext of the computing environment 100 but may instead be implementedby other systems described herein or other computing systems not shown.The process 200 provides one example approach by which the end usersystem 102 can obtain a universal identifier for identifying visitordata related to the end user system's interactions with the content site110.

At block 202, an end user system 102 can request content such as acontent page 112 from the content site 110. The end user system 102 mayreceive the content page 112 including a tag container 114 at block 204.Receipt of the content page 112 may further initiate the creation orupdating of a piece of data, such as a cookie, associated with thebrowser 103 of the end user system 102 and usable to store data aboutend user system interactions with the content site 110. At block 206,the end user system 102 can request one or more tags 116, 118 associatedwith the tag container 114 from a tag server 120. The tag container 114may include script code such as JavaScript code or the like embedded inthe source of the content page 112 initially requested by the end usersystem 102. The script can reference one or more tags 116, 118. The tagcontainer 114, upon being processed by the browser 103, canprogrammatically access the tag(s) 116 or 118 (or other tag) stored onthe tag server 120 to request the tag(s) 116 or 118 to be provided ordownloaded to the end user system 102. The tag(s) 116, 118 may each be astatic file or the like that includes executable code such as HTML codeand/or script code, such as JavaScript or the like.

The tag(s) 116 or 118 can be received at block 208 at the end usersystem 102, and the tag(s) 116 or 118 can be executed at block 210 bythe end user 102 system. Upon execution of the tag 118, at block 212,the browser 103 can obtain a universal identifier associated with theend user system 102. The way in which this universal identifier isobtained can be based at least on whether the end user system 102 haspreviously visited the content site 110 or one or more other settings orcriteria. In certain embodiments, the end user system 102 can determinewhether the end user system 102 previously visited the content site 110according to whether a first-party cookie may be stored on the end usersystem 102. In other embodiments, the end user system 102 can determinewhether the end user system 102 previously visited the content site 110based on whether the first-party cookie stores a particular type ofidentification or value, such as a universal identifier from theidentification subsystem 152.

In some embodiments, when the end user system 102 has not previouslyvisited the content site 110, the browser 103 can locally generate auniversal identifier for the end user system 102 using an algorithm, alookup table, or the like. The locally generated universal identifiercan be based at least on one or more of a media access control (MAC)address, Internet Protocol (IP) address, browser user agent, or the likeassociated with the end user system 102 or browser 103. Additionally oralternatively, the browser 103 can send identification data associatedwith the end user system 102 to the identification subsystem 152. Forexample, the browser 103 can send one or more first-party or third-partycookies including a tracking identifier to the identification subsystem152. The first-party or third-party cookie may, in some embodiments,include the generated universal identifier, which the identificationsubsystem 152 can store. A “first-party cookie,” in addition to havingits ordinary meaning, as used herein can include a cookie belonging tothe same domain as the content site 110. A “third-party cookie,” inaddition to having its ordinary meaning, as used herein can include acookie belonging to a domain other than the domain of the content site110, like the domain of the identification subsystem 152. Third-partycookies are described in greater detail below. The identificationsubsystem 152, in response to the identification data, can transmit auniversal identifier associated with the end user system 102, and theend user system 102 can receive the universal identifier. In someembodiments, the identification subsystem 152 can provide the identifierincluded in the received first-party or third-party cookie as theuniversal identifier.

In some embodiments, when the end user system 102 has previously visitedthe content site 110, the tag 118 can obtain the universal identifierfrom a first-party cookie stored on the end user system 102. The enduser system 102, in such cases, may presume that a tracking identifierof the first-party cookie can be the universal identifier for the enduser system 102.

The browser 103 can process the universal identifier at block 214according to the executable code of the tag 118. The browser 103 can,for instance, assign the universal identifier as a unique visitoridentifier for the content site 110 to use when tracking interactionsbetween the content site 110 and the end user system 102. In addition,the tag 118 may update or modify the content page 112 to include theuniversal identifier, such as by updating the Document Object Model(DOM) of the content page 112. For instance, the tag 118 may add theuniversal identifier to a data object or data layer of the content page112 (e.g., the document object model (DOM) thereof), sometimes referredto herein as a universal data object (UDO). By updating or modifying thecontent page 112 with the universal identifier, the tags 116, 118 thatmay not have native access to the universal identifier can access theidentifier by reading the modified portion of the content page. One ormore of the tags 116, 118 can also add the identifier value to afirst-party or third-party cookie, such as in a tracking identifier ofthe first-party or third-party cookie, for later reference.

Additionally, at block 212, upon execution of one or more of the tags116, 118, the browser 103 can obtain the universal identifier andvisitor data about the end user system 102. The universal identifier andvisitor data can be retrieved, for example, by reading a portion of thecontent page or accessing data stored in a first-party or third-partycookie. The visitor data can include any of a variety of informationabout the end user system 102 and the end user system's interactionswith the content site 110. For instance, the visitor data may includeinformation about what type of browser 103 or application used to accessthe content site 110. The visitor data may also include informationabout a geographic location of the user, a duration that the useraccessed the content site 110 or logged into the content site, or thelike. In addition, the visitor data can include information about anyinteraction by the visitor with the content site 110 including, forexample, any clicks made by the visitor on links on the content page 112served by the content site 110, any user selection of a form element, orany user scroll behavior, text entry behavior in form text boxes, chatboxes, e-mail boxes, social networking, other user interaction withother user interface controls, combinations of the same, or the like.

At block 216, the browser 103 can send the universal identifier and someor all of the visitor data to processing systems like the visitorprocessing system 140 or the tag vendor systems 170, according to theexecutable code of one or more of the tags 116, 118. The universalidentifier can be sent in association with the visitor data so that thevisitor data attributable or related to the universal identifier may beunderstood as attributable or related to the universal identifier by thesystems 140, 170. As a result, after the visitor data may be processedby the systems 140, 170, the processed data can be collected andevaluated using the universal identifier to determine the processed datafrom each of the systems 140, 170 that is related to the universalidentifier.

In certain embodiments, the process 200 is notably different than atraditional process for utilizing a cookie of the browser 103. In atraditional process, when the content page 112 is requested by the enduser system 102, a cookie stored on the end user system 102 andassociated with the content page 112 may be sent to the content site110. The content site 110, in response, can send a version of thecontent page 112 that is tailored based on the information contained inthe cookie, such as shopping cart contents, button clicks, andpreviously visited pages. In contrast, according to some embodiments ofthe process 200, the end user system 102 can send identification data,such as one or more cookies, associated with the end user system 102 tothe identification subsystem 152. The identification subsystem 152, inresponse, can transmit a universal identifier to the end user system102. When the tag 118 may process the universal identifier, the tag 118can update or modify the earlier downloaded content page 112 to includethis universal identifier.

FIG. 3 depicts an embodiment of a universal identifier contentmanagement system process 300. The process 300 illustrates an examplemode of operation of the computing environment 100 of FIG. 1 and may beimplemented by the various components shown in the computing environment100 of FIG. 1 . For convenience, the process 300 is described in thecontext of the computing environment 100 but may instead be implementedby other systems described herein or other computing systems not shown.The process 300 provides one example approach by which the content site110 and the visitor intelligence system 180 together can enable visitorsto the content site 110 to be uniquely identified, facilitating theevaluation of processed or raw data from the visitor processing system140 and the tag vendor systems 170 on an individual visitor basis.

At block 302, the content site 110 can receive multiple requests for thecontent page 112 from the end user systems 102. In response, at block304, the content site 110 can send the content page 112 including a tagcontainer 114 to the end user systems 102, causing the end user systems102 to send visitor data with associated universal identifiers tomultiple processing systems. For example, as described with respect tothe process 200, when the tag containers 114 may be processed by thebrowsers 103 of the end user systems 102, the browsers 103 can accessthe tags 116, 118. Upon execution of one or more of the tags 116, 118,the browsers 103 can individually obtain a universal identifier usablefor tracking interactions between the content site 110 and the end usersystems 102. These universal identifiers and associated visitor data maythen be provided to the processing systems, like the visitor processingsystem 140 or the tag vendor systems 170, according to one or more ofthe tags 116, 118.

At block 306, the visitor intelligence system 180 can receive data fromthe processing systems that can be related to end user systeminteractions with the content page 112 and organizable by the universalidentifiers. The visitor intelligence system 180, for instance, canreceive the processed data (as well as raw visitor data) from thevisitor processing system 140 or the tag vendor systems 170. Theprocessed data can include indications of portions of the processed datathat can be attributable or related to one or more particular universalidentifiers and thus one or more particular end user systems 102. Thevisitor intelligence system 180 can thereby evaluate the processed datausing the universal identifiers at block 308 to facilitate, for example,consideration of the impact of actions reflected across multipleprocessed data sets from different providers. In one implementation, thevisitor intelligence system 180 can present a report that listsprocessed data provided by multiple vendors, as shown in FIG. 7 .

FIG. 4 depicts an embodiment of a universal identifier generationprocess 400. The process 400 illustrates an example mode of operation ofthe computing environment 100 of FIG. 1 and may be implemented by thevarious components shown in the computing environment 100 of FIG. 1 .For convenience, the process 400 is described in the context of thecomputing environment 100 but may instead be implemented by othersystems described herein or other computing systems not shown. Theprocess 400 provides one example approach by which the identificationsubsystem 152 can determine a universal identifier for identifyingvisitor data about an end user system's interactions with the contentsite 110.

At block 402, the identification subsystem 152 can receiveidentification data associated with the end user system 102 from thebrowser 103. The identification subsystem 152, for instance, can receiveone or more first-party or third-party cookies, including trackingidentifiers for the content site 110 or the identification subsystem152.

The identification system 152 can use the identification data todetermine a universal identifier at block 404. The universal identifiercan be a unique visitor identifier for the content site 110 usable totrack interactions between the content site 110 and the end user system102. If a universal identifier associated with the end user system 102has been previously determined by the identification system for thecontent site 110, the identification system can determine the sameuniversal identifier for the end user system 102 so that interactionsbetween the end user system 102 and the content site 110 can be easilytracked over time. In some embodiments, the identification system mayadopt an identifier from the identification data provided by the enduser system 102, such as the tracking identifier in a first-party orthird-party cookie, or generate the universal identifier according to analgorithm, a lookup table, or the like.

In further embodiments, the identification subsystem 152 can selectivelyor periodically determine a new universal identifier for the end usersystem 102, such as when the identification system 152 determines thatthe universal identifier for the end user system 102 conflicts with auniversal identifier for another end user system or to enhance securityof the universal identifiers or related information over time. Moreover,in some embodiments, when a universal identifier may have beenpreviously determined for the end user system 102 but for a differentcontent site, the identification system 152 can determine the sameuniversal identifier for the end user system 102 for both content sitessuch that interactions between the end user system 102 and both sitescan be monitored, as described in greater detail with respect to FIG. 6. In certain embodiments, the identification subsystem 152 canadditionally or alternatively manage different identifiers for the enduser system 102 for one or more different content sites and track anassociation between the end user system 102 and the differentidentifiers to monitor the end user system 102 activity. For instance,the identification subsystem 152 can maintain a data structure such as aqueue or list for the end user system 102 and add each of the differentidentifiers to the data structure with an indication of the associatedone or more different content sites.

At block 406, the identification subsystem 152 sends the universalidentifier to the end user system 102. The identification subsystem 152,for example, can send to the browser 103 one or more first-party orthird-party cookies that include the universal identifier. Upon receiptof the universal identifier, the end user system 102 can send visitordata about the end user system 102 with the universal identifier toprocessing systems, such as the visitor processing system 140 or the tagvendor systems 170, thereby enabling the processing systems to associatethe visitor data specifically with the end user system 102.

In certain embodiments, the identification subsystem 152 isadvantageously implemented as a subsystem of the tag management system150 of the analytics system 130. Since the analytics system 130 mayalready manage and configure the tags 116, 118 associated with the tagcontainer 114, the tag management system 150 can be in the uniqueposition to push the universal identifier to appropriate variables ofthe tags 116, 118. That is, the analytics system 130 can manage amapping of the variables receivable by the visitor processing system 140and the tag vendor systems 170 so that a minimal amount of coding may beused to implement the universal identifier for the content page 112. Insome embodiments, the identification subsystem 152 can instead be partof one of the tag vendor systems 170 rather than a subsystem of theanalytics system 130.

FIG. 5 depicts an embodiment of a computing environment for identifyingvisitors to a content site using the computing environment of FIG. 1 .The computing environment 500 includes a browser, such as the browser103 of the end user system 102, in a state 510 where the browser loads apage of a content site. State transitions are represented by circlednumbers in the diagram.

In response to the browser 510 loading the page of the content site, asdescribed with respect to the process 200, the browser 510 can executean identification tag of the page that causes the browser 510 to obtainor generate a universal identifier and update the page to include theobtained universal identifier. The browser 510 further can execute oneor more tags of the page that cause the browser 510 to obtain theuniversal identifier from the updated page and to send visitor dataalong with the universal identifier to the tag vendor systems 170 viastate 1. The universal identifier can be sent in association with thevisitor data so that the visitor data attributable or related to theuniversal identifier can be understood as attributable or related to theuniversal identifier by the tag vendor systems 170.

The tag vendor systems 170 can process the visitor data andcorresponding universal identifiers from the browser 510. One or more ofthe tag vendor systems 170 can, for instance, determine analytics fordata analysis or business intelligence for the end user system 102,track affiliate activity with respect to the content site, obtain userdata for the end user system 102 for displaying targeted ads, obtainuser data for the end user system 102 for customizing searchfunctionality or email campaigns targeted to the end user, obtaininguser data for personalizing content of the page for the end user system102, obtain user data for the end user system 102 for integration withsocial networking functionality, obtain user data for the end usersystem 102 for big data analysis, combinations of the same, or the like.The processed data from the tag vendor systems 170 can be transferredvia states 2 and 3 to the visitor intelligence system 180. The visitorintelligence system 180 can accordingly organize or evaluate theprocessed data using the universal identifier of the end user system 102or prepare a cross-vendor profile for the end user system 102.

FIG. 6 depicts an embodiment of a computing environment 600 foridentifying visitors across different content sites using the computingenvironment 100 of FIG. 1 . The computing environment 600 includes abrowser, such as the browser 103 of the end user system 102, in onestate 610A where the browser loads a page of content site A and anotherstate 610B where the browser loads a page of content site B. The contentsites A and B can correspond to different domains owned or operated bythe same content provider, in some embodiments. State transitions arerepresented by circled numbers in the diagram.

In response to the browser 610A loading the page of content site A, thebrowser 610A can execute an identification tag of the page of contentsite A that causes the browser 610A to send identification data, such asone or more first-party or third-party cookies associated with thebrowser 610A, to the identification subsystem 152 via state 1. Thefirst-party cookie may be a cookie stored by the content site A on thebrowser's end user system 102 while the third-party cookie may be acookie stored by the identification subsystem 152 on the browser's enduser system 102. Each of the first-party and third-party cookies caninclude one or more tracking identifiers assigned to the end user system102 by the provider of the cookie.

The identification subsystem 152 can receive the identification dataand, in return, provide a corresponding universal identifier for the enduser system 102 via state 2. In certain embodiments, the browser 610Aprovides at least a third-party cookie stored by the identificationsubsystem 152 on the end user system 102 to the identification subsystem152. The identification subsystem 152 then returns a copy of thisthird-party cookie. If no third-party cookie has been stored by theidentification subsystem 152 on the end user system 102 or if athird-party cookie may have been previously stored and was subsequentlydeleted from the end user system 102, the browser 610A can provide atleast a first-party cookie stored by the content site A on the end usersystem 102 to the identification subsystem 152. The identificationsubsystem 152 subsequently returns a copy of a portion of thefirst-party cookie as a third-party cookie. After receiving thethird-party cookie from the identification subsystem 152, the browser610A can treat the tracking identifier in the received third-partycookie as the universal identifier and accordingly transfer thistracking identifier to a tracking identifier in the first-party cookiestored by the content site A. The browser 610A can additionally updatethe page of the content site A (e.g., the document object model (DOM)thereof) to include the universal identifier.

Upon execution of one or more tags of the content site A, the browser610A obtains the universal identifier from the updated page of thecontent site A and sends visitor data, along with the universalidentifier stored in the first-party cookie, to the tag vendor systems170 via state 3. The universal identifier can be sent in associationwith the visitor data so that the visitor data attributable or relatedto the universal identifier can be understood as attributable or relatedto the universal identifier by the tag vendor systems 170.

In response to the browser 610B loading the page of content site B, thebrowser 610B can execute an identification tag of the page of contentsite B that causes the browser 610B to send identification data, such asone or more first-party or third-party cookies associated with thebrowser 610B, to the identification subsystem 152 via state 4. Thefirst-party cookie can be a cookie stored by the content site B on thebrowser's end user system while the third-party cookie can be a cookiestored by the identification subsystem 152 on the browser's end usersystem. Each of the first-party and third-party cookies can include oneor more tracking identifiers assigned to the end user system 102 by theprovider of the cookie.

The identification subsystem 152 can receive the identification dataand, in return, provide via state 5 the same corresponding universalidentifier to the end user system 102 that was provided via state 2. Incertain embodiments, the browser 610B provides at least a third-partycookie stored by the identification subsystem 152 on the end user system102 to the identification subsystem 152. The identification subsystem152 then returns a copy of this third-party cookie. After receiving thethird-party cookie from the identification subsystem 152, the browser610B can treat the tracking identifier in the received third-partycookie as the universal identifier and transfer this tracking identifierto a tracking identifier in the first-party cookie stored by the contentsite B. The browser 610B can additionally update the page (e.g., the DOMthereof) of the content site B to include the universal identifier.

Upon execution of one or more tags of the content site B, the browser610B obtains the universal identifier from the updated page of thecontent site B and sends visitor data, along with the universalidentifier stored in the first-party cookie, to the tag vendor systems170 via state 6. The universal identifier can be sent in associationwith the visitor data so that the visitor data attributable or relatedto the universal identifier can be understood as attributable or relatedto the universal identifier by the tag vendor systems 170.

The tag vendor systems 170 can process the visitor data andcorresponding universal identifiers from the browser in the states 610Aand 610B. One or more of the tag vendor systems 170 can, for instance,determine analytics for data analysis or business intelligence for theend user system 102, track affiliate activity with respect to thecontent site A or B, obtain user data for the end user system 102 fordisplaying targeted ads, obtain user data for the end user system 102for customizing search functionality or email campaigns targeted to theend user, obtaining user data for personalizing content of the contentpages A and B for the end user system 102, obtain user data for the enduser system 102 for integration with social networking functionality,obtain user data for the end user system 102 for big data analysis,combinations of the same, or the like. The processed data from the tagvendor systems 170 can be transferred via states 7 and 8 to the visitorintelligence system 180. The visitor intelligence system 180 canaccordingly organize or evaluate the processed data using the universalidentifier of the end user system 102 or prepare a cross-vendor profilefor the end user system 102.

In certain examples discussed with respect to FIG. 6 , the examplesdescribe utilizing tracking identifiers of cookies to exchange auniversal identifier or identification data. This implementation hasbeen selected in part to address security limitations imposed in somecomputing environments. For instance, in some cases, a first-partycookie for a content site within one domain may not be accessed by acontent site from a different domain. As a result, a third-party cookieassociated with both domains can be used to keep the universalidentifiers consistent between multiple content sites and domains asdescribed with respect to FIG. 6 . Accordingly, in other computingenvironments, one or more other approaches for requesting, determining,or transmitting the universal identifier and the identification data caninstead be implemented.

In certain embodiments, one or more examples discussed with respect toFIG. 6 can be understood in contrast to a computing environment where anidentification system shares a third-party cookie and relies onredirection, such as via a proxy functionality, to facilitateidentification of end user systems. The one or more examples can insteadrely on copying one or more values from a first-party or third-partycookie. As a result, the one or more examples can, in some instances,provide one or more of numerous advantages, including (1) removing adependency on a redirection system that may be unavailable at times andthereby cause end user system identification to not be possible, (2)providing an identification source for end user systems via a mechanismother than a redirection system, (3) reducing a number of networkcommunications (by avoiding sharing a cookie) and thereby reducingnetwork latency and improving computing performance, (4) providingredundancy for identification of end user systems, and (5) providing anefficient, open architecture whereby an identifier may be widelyaccessed, such as by multiple digital tags provided by one or morevendors that may but need not include a provider of a tag managementsystem.

FIG. 7 depicts an embodiment of a reporting user interface 700. Theinterface 700 can be output by the visitor intelligence system 180 fordisplay by the browser 105 of the tag management user systems 104 fortag management users. The data included in the interface 700 may besupplied by the content site 110, the analytics system 130, the tagvendor systems 170, or the visitor intelligence system 180. In someembodiments, the visitor intelligence system 180 alone supplies the datashown in the interface 700. The interface 700 can advantageously, incertain embodiments, display cross-vendor information for particularuniversal identifiers associated with the content site 110 so thatdisparate processed data from the visitor processing system 140 and thetag vendor systems 170 may be shown relative to the same universalidentifiers. The cross-vendor information can beneficially be used bythe tag management users to evaluate the impact of previous visitorinteractions with the content site 110 and plan approaches for futurechanges to the content site 110.

The interface 700 includes multiple selection options for controllingthe data displayed in the interface 700. Using the “Select ID Group”drop-down 710, the tag management users can select to review data for asubset of universal identifiers associated with the content site 110.For instance, the interface 700 shows a subset group “Group 123” thatincludes universal identifiers ranging from 100,000 to 100,008. Usingthe “Select Attribute” drop-down 720, the tag management users canadditionally select to review particular attributes for the selectedsubset of universal identifiers. For example, by selecting the“Advertising Characteristics” attribute, the interface 700 may displayparticular vendor metrics related to advertising characteristics of theuniversal identifiers.

As illustrated in FIG. 7 , in some embodiments, the interface 700 candisplay three vendor metrics corresponding a subset of universalidentifiers, where each vendor metric is provided by a different vendor.The three vendor metrics together can provide a more complete picture ofthe advertising characteristics for individual universal identifiersthan any one of the vendor metrics individually. The Vendor 1 Metric canindicate a sensitivity of individual universal identifiers to certaintypes of advertising information. For example, the end user system 102associated with a particular universal identifier may be more likely tomake purchases when confronted with feedback about a product or service(i.e., a feedback-sensitive purchaser), when offered rush deliveryoptions (i.e., a time-sensitive purchaser), or when offered discounts(i.e., a price-sensitive purchaser). The Vendor 2 Metric can indicate aninterest or category preference associated with individual universalidentifiers. For instance, the end user system 102 associated with aparticular universal identifier may be more likely to make purchaseswhen presented with advertisements related to sporting equipment,electronics, home and garden, beauty and health, or movies and music.The Vendor 3 Metric can indicate an assessment of the likely businessvalue associated with individual user identifiers. For example, the enduser system 102 associated with a particular universal identifier may bemore likely to result in a relatively large profit (i.e., high value), arelatively average amount of profit (i.e., medium value), or arelatively small amount of profit (i.e., low value) when presented withan advertisement. Based on this information, tag management users candesirably tailor approaches and investments when advertising toindividual end user systems.

The user interface controls shown in FIG. 7 are merely illustrativeexamples and can be varied in other embodiments. For instance, buttons,dropdown boxes, select boxes, text boxes, check boxes, slider controls,and other user interface controls shown may be substituted with othertypes of user interface controls that provide the same or similarfunctionality. Further, the user interface controls may be combined ordivided into other sets of user interface controls such that similarfunctionality or the same functionality may be provided with verydifferent looking user interfaces. Moreover, each of the user interfacecontrols may be selected by a user using one or more input options, suchas a mouse, touch screen input, or keyboard input, among other userinterface input options.

IV. Detailed Example Computing Environment

Turning to FIG. 8 , a more detailed example embodiment of a computingenvironment 800 is shown that can perform any of the analytics featuresdescribed herein. The computing environment 800 is a more detailedexample of implementation of the computing environment 100 of FIG. 1 .As in FIG. 1 , end user systems 102 are shown in communication withcontent sites 110 which may communicate over a network (not shown). Inaddition, tag management user systems 104 are also shown. The computingenvironment 800 facilitates implementation of an analytics system 840,which may include the functionality of the analytics system 130described above.

In the depicted embodiment, the analytics system 840 is showndistributed in a cloud platform that provides redundant andgeographically dispersed access to the analytics system 840. Inparticular, the analytics system 840 is implemented in various cloudregions 872. These cloud regions may be implemented in any type of cloudplatform, which may simply be a data center operated by a vendor of theanalytics system or by a third-party vendor such as Amazon WebServices™, Microsoft Azure™, Rackspace™, Linode™, combinations of thesame, or the like. Each cloud region 872 includes a load balancer 876that can balance requests to analytics system instances 840.

The analytics system instances 840 can be implemented as virtualmachines and/or physical machines. In the Amazon Web Servicesembodiment, the instances 840 can be elastic compute cloud (EC2)instances that are distributed geographically for faster and redundantaccess to geographically dispersed analysis user systems 104. Inaddition, visitor profile data storage devices 830 are shown in thedifferent cloud regions 872 and can store tag and visitor data in thecloud. Virtual private network (VPN) tunnels 880 facilitate securecommunication in a virtual private network among the different cloudregions 872 and enable administrator users (not shown) of the analyticssystem to access analytics system instances 840.

In an embodiment, the virtual private network is facilitated or providedby a private cloud service, such as the Virtual Private Cloud (VPC)service provided by Amazon Web Services™. The private cloud service canprovide security to the analytics system instances 840 by virtue ofobscuring IP addresses of the analytics instances 840. The analyticssystem instances 840 may have nonpublic IP addresses so that eachanalytics system instance 840 does not need to have security softwarethat is responsible for securing the analytics system 840 itself.

A geodns provider 860 is provided for interfacing between content sites110, analysis user systems 104, and the various analytics systeminstances 840. The geodns provider 860 also provides access to publishedtags 890 which are stored in tag servers 894 accessible through one ormore or content delivery networks (CDNs) 892. The function of the geodnsprovider 860 in one embodiment is to periodically determine which CDNhosting the tags has the lowest latency, thereby selecting which CDN topoint the content site 110 to when accessing tags on the tag servers894. The geodns provider 860 may implement the DYN DNS system in oneembodiment.

Advantageously, in certain embodiments, by storing tags in CDNs, tagaccess can be much faster than if tags were stored in locally hosted tagservers. Further, by using a geodns provider 860, access to tags can beeven more rapidly achieved by cycling through the fastest available CDNs892.

V. Additional Embodiments and Terminology

Many other variations than those described herein will be apparent fromthis disclosure. For example, depending on the embodiment, certain acts,events, or functions of any of the algorithms described herein can beperformed in a different sequence, can be added, merged, or left outaltogether (e.g., not all described acts or events are necessary for thepractice of the algorithms). Moreover, in certain embodiments, acts orevents can be performed concurrently, e.g., through multi-threadedprocessing, interrupt processing, or multiple processors or processorcores or on other parallel architectures, rather than sequentially. Inaddition, different tasks or processes can be performed by differentmachines and/or computing systems that can function together.

In some embodiments, the universal identifier does not includepersonally identifiable information (e.g., email address, loginusername, rewards member number, or the like, that can be associatedwith the end user system 102) so as to avoid making such informationknown to multiple vendors. Alternatively, at least some of thisadditional information may be used (e.g., with user permission) inaddition to or instead of tracking a universal identifier of afirst-party or third-party cookie. For example, the universal identifierincluding this additional information can be provided by the end usersystem 102 to the visitor processing system 140 or the tag vendorsystems 170 as a result of executing of one of the tags 116, 118. Inanother example, the universal identifier including this additionalinformation can be provided by the identification subsystem 152 to theend user system 102 and, in turn, provided by the end user system 102 tothe visitor processing system 140 or the tag vendor systems 170 as aresult of executing of one of the tags 116, 118. Moreover, in certainembodiments, the content page 112 may not include a tag container 114 asillustrated in FIG. 1 . Instead, the tags 116, 118 can be directly codedin the content page 112.

In some embodiments, personally identifiable information (e.g., emailaddress, login username, rewards member number, or the like, that can beassociated with the end user system 102) can be used to match multipleuniversal identifiers to a single end user. For example, a visitor to acontent page 112 may visit the content page 112 using one or moredevices, such as a mobile device, a laptop, and a desktop computer. Eachof these devices may be assigned a different universal identifier.Without additional information, each of these devices may be treated asa different visitor to the content page 112. However, using thepersonally identifiable information, the different universal identifiersfor the end user's devices can advantageously be associated with thesame end user. In some embodiments, the identification subsystem 152 canassociate the personally identifiable information with the universalidentifiers and provide matching universal identifiers to the devices sothat each of the devices has the same universal identifier. Accordingly,the same universal identifier can be associated both across differentcontent sites and across different end user devices in certainimplementations. Alternatively or additionally, the visitor intelligencesystem 180 may match the processed data associated with differentuniversal identifiers using the personally identifiable information.

In an embodiment, a method of identifying user data associated with auser of a content page can be performed under control of anidentification system comprising a physical computing device includingdigital logic circuitry. The method can include receiving, from a usersystem, identification data associated with a content site. Theidentification data can include first data corresponding to a domain ofthe content site and second data corresponding to a domain of theidentification system. The method can further include in response tosaid receiving the identification data, transmitting to the user systeman identifier determined based at least on the second data and usable bythe content site to identify the user system. In one example, the firstdata can include a first-party cookie, and the second data can include athird-party cookie including the identifier. Moreover, the method ofthis paragraph can be performed by a system including one or more memorydevices and one or more hardware processors in communication with theone or more memory devices.

In another embodiment, a method of identifying user data associated witha user of a content page can be performed under control of a contentmanagement system comprising a physical computing device includingdigital logic circuitry. The method can include receiving a request froma user system for a content page stored in a content server. Inaddition, the method can include transmitting to the user system thecontent page and a data collection tag container including executablecode that when executed by the user system causes the user system toobtain one or more tags. The one or more tags can include executablecode that when executed by the user system causes the user system toobtain a visitor identifier, modify the content page to include thevisitor identifier, and transmit the visitor identifier obtained fromthe modified content page and visitor data associated with the usersystem to one or more analysis systems. Moreover, the method of thisparagraph can be performed by a system including one or more memorydevices and one or more hardware processors in communication with theone or more memory devices.

The various illustrative logical blocks, modules, and algorithm stepsdescribed in connection with the embodiments disclosed herein can beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. The described functionality can be implemented invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the disclosure.

The various illustrative logical blocks and modules described inconnection with the embodiments disclosed herein can be implemented orperformed by a machine, such as a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general purpose processor can be a microprocessor,but in the alternative, the processor can be a controller,microcontroller, or state machine, combinations of the same, or thelike. A hardware processor can include electrical circuitry or digitallogic circuitry configured to process computer-executable instructions.In another embodiment, a processor includes an FPGA or otherprogrammable device that performs logic operations without processingcomputer-executable instructions. A processor can also be implemented asa combination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration. A computing environment can include any type of computersystem, including, but not limited to, a computer system based on amicroprocessor, a mainframe computer, a digital signal processor, aportable computing device, a device controller, or a computationalengine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module stored in one or more memory devices andexecuted by one or more processors, or in a combination of the two. Asoftware module can reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of non-transitory computer-readable storagemedium, media, or physical computer storage known in the art. An examplestorage medium can be coupled to the processor such that the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium can be integral to the processor.The storage medium can be volatile or nonvolatile. The processor and thestorage medium can reside in an ASIC.

Conditional language used herein, such as, among others, “can,” “might,”“may,” “e.g.,” and the like, unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain embodiments include, while other embodiments donot include, certain features, elements and/or states. Thus, suchconditional language is not generally intended to imply that features,elements and/or states are in any way required for one or moreembodiments or that one or more embodiments necessarily include logicfor deciding, with or without author input or prompting, whether thesefeatures, elements and/or states are included or are to be performed inany particular embodiment. The terms “comprising,” “including,”“having,” and the like are synonymous and are used inclusively, in anopen-ended fashion, and do not exclude additional elements, features,acts, operations, and so forth. Also, the term “or” is used in itsinclusive sense (and not in its exclusive sense) so that when used, forexample, to connect a list of elements, the term “or” means one, some,or all of the elements in the list. Further, the term “each,” as usedherein, in addition to having its ordinary meaning, can mean any subsetof a set of elements to which the term “each” is applied.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, certain embodiments of the inventions described herein canbe embodied within a form that does not provide all of the features andbenefits set forth herein, as some features can be used or practicedseparately from others.

1-20. (canceled)
 21. A method for collecting and identifying user dataassociated with user interactions with a content page, the methodcomprising: under control of a physical computing device comprising ahardware processor and a memory device: loading a content page of acontent site in the memory device; outputting the content page forpresentation on a display to a user of the physical computing device;adding an identifier to the content page so that the identifier isaccessible from the content page by a first tag and a second tag, theidentifier being usable to identify the physical computing deviceseparately from other physical computing devices that load the contentpage; executing a script of the first tag to: retrieve the identifierfrom the content page, gather first data indicative of first userinteractions with the content page, and transmit the first data inassociation with the identifier retrieved from the content page to afirst processing system; and executing a script of the second tag to:retrieve the identifier from the content page, gather second dataindicative of second user interactions with the content page, andtransmit the second data in association with the identifier retrievedfrom the content page to a second processing system different from thefirst processing system.
 22. The method of claim 21, wherein said addingthe identifier to the content page comprises adding the identifier to adata object of the content page.
 23. The method of claim 21, whereinsaid adding the identifier to the content page comprises adding theidentifier to a data layer of the content page.
 24. The method of claim21, wherein the identifier does not comprise personally identifiableinformation.
 25. The method of claim 21, further comprising determining,under control of the physical computing device, the identifier withoutusing personally identifiable information.
 26. The method of claim 21,further comprising determining, under control of the physical computingdevice, the identifier by looking up the identifier in a data filestored on the memory device and associated with the content site. 27.The method of claim 21, wherein the first tag and the second tag do nothave native access to the identifier.
 28. The method of claim 21,further comprising: under control of the physical computing device:loading another content page of another content site in the memorydevice, the another content site belonging to a different domain fromthe content site; outputting the another content page for presentationon the display; adding the identifier to the another content page sothat the identifier is accessible from the another content page by athird tag; and executing a script of the third tag to: retrieve theidentifier from the another content page, gather third data indicativeof third user interactions with the another content page, and transmitthe third data in association with the identifier retrieved from theanother content page to a third processing system.
 29. The method ofclaim 21, wherein the first user interactions and the second userinteractions are the same.
 30. The method of claim 21, wherein the firstuser interactions and the second user interactions are different. 31.The method of claim 21, wherein the first processing system comprises afirst server, and the second processing system comprises a second serverdifferent from the first server.
 32. The method of claim 21, furthercomprising receiving, under control of the physical computing device,the first tag and the second tag via a computer network.
 33. The methodof claim 21, wherein said outputting the content page comprisesoutputting the content page for presentation in a browser.
 34. Themethod of claim 21, wherein the first data comprises data indicative ofselection of an item of the content page by the user.
 35. An apparatusfor collecting and identifying user data associated with userinteractions with a content page, the apparatus comprising: a physicalcomputing device comprising: a memory device; and a hardware processorin communication with the memory device, the hardware processor beingconfigured to: load a content page of a content site in the memorydevice; output the content page for presentation on a display to a userof the physical computing device; add an identifier to the content pageso that the identifier is accessible from the content page by a firsttag and a second tag, the identifier being usable to identify thephysical computing device separately from other physical computingdevices that load the content page; execute a script of the first tagto: retrieve the identifier from the content page, gather first dataindicative of first user interactions with the content page, andtransmit the first data in association with the identifier retrievedfrom the content page to a first processing system; and execute a scriptof the second tag to: retrieve the identifier from the content page,gather second data indicative of second user interactions with thecontent page, and transmit the second data in association with theidentifier retrieved from the content page to a second processing systemdifferent from the first processing system.
 36. The apparatus of claim35, wherein the hardware processor is configured to add the identifierto a data object of the content page or a data layer of the contentpage.
 37. The apparatus of claim 35, wherein the identifier does notcomprise personally identifiable information.
 38. The apparatus of claim35, wherein the first tag and the second tag do not have native accessto the identifier.
 39. The apparatus of claim 35, wherein the hardwareprocessor is configured to: load another content page of another contentsite in the memory device, the another content site belonging to adifferent domain from the content site; output the another content pagefor presentation on the display; add the identifier to the anothercontent page so that the identifier is accessible from the anothercontent page by a third tag; and execute a script of the third tag to:retrieve the identifier from the another content page, gather third dataindicative of third user interactions with the another content page, andtransmit the third data in association with the identifier retrievedfrom the another content page to a third processing system.
 40. Theapparatus of claim 35, wherein the hardware processor is configured toreceive the first tag and the second tag via a computer network, and thefirst processing system comprises a first server and the secondprocessing system comprises a second server different from the firstserver.